-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Blog] Creating a new blog post seven-kubernetes-pitfalls-and-how-to-avoid #49249
base: main
Are you sure you want to change the base?
[Blog] Creating a new blog post seven-kubernetes-pitfalls-and-how-to-avoid #49249
Conversation
Signed-off-by: lhajouji <[email protected]>
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Overall I think this blog's structure and. content look great. One thing that I think can be imporved is adding some more description to the pitfalls of every section. For example, for the third point it would be great to provide some more context as to why the logs get lost after some time. Similarly more details for the reasons for the other pitfalls |
@siddhant-khisty Thanks for the valuable review ! i'll try to add this detail. |
Adding some context to the first pitfall.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
This is a request to create a blog post that walks readers through seven common Kubernetes pitfalls, which can trip up both beginners and experienced practitioners.
Thanks in advance for your consideration.